To monitor the operational performance of a SpinServer system's hardware and software functions, configure the event commands to display and receive email messages of warnings about equipment and procedure failure and information about equipment setup procedures that complete successfully. The event command node includes the following subnode commands:
alarm
filters
log
notification
spinevents
syslog
Each of the subnode commands, and the leaf-node commands attached to them, is described in detail, with parameters and arguments listed for each command.
Examples of command usage are included in the discussions.
To view the current states of alarm variables for a SpinServer system, use the event alarm show command.
CLI:
event alarm show [-index index_listing]
GUI: Navigate to the Event → Alarms node. To display information about a specific alarm, select it from the table and run the Show command from the drop-down menu in the action pane.
The event alarm show command displays the current states of alarms. Used without the -index parameter, the command displays the following information:
Index
Variable status
Current value. Possible values include the following:
OK (The alarm is in the normal range.)
Alarm (The alarm is in a state that indicates a problem.)
---- (The alarm sensor is not sensing.)
Use the optional -index parameter to receive information about a specific alarm.
The following example displays the current states of alarm variables.
spinserver::> event alarm show
Index Instance Variable Status Current
Value
0 CPU 1 Fan sensorValue OK 4115
1 CPU 2 Fan sensorValue Alarm 2647
2 Chassis Intake Fan 1 sensorValue Alarm 0
3 Chassis Intake Fan 2 sensorValue Alarm 0
4 Chassis Intake Fan 3 sensorValue Alarm 0
5 Chassis Intake Fan 4 sensorValue Alarm 0
6 Chassis Exhaust Fan 1 sensorValue Alarm 0
7 Motherboard Temperature 1 sensorValue OK 33
8 Motherboard Temperature 1 sensorValue Alarm 33
9 CPU 1 Temperature sensorValue Alarm 16
10 CPU 1 Temperature sensorValue OK 16
11 Motherboard Temperature 2 sensorValue OK 35
12 Motherboard Temperature 2 sensorValue Alarm 35
13 CPU 2 Temperature sensorValue Alarm 165
14 CPU 2 Temperature sensorValue Alarm 165
15 Power supply monitor failed Alarm false
The following example displays the current status of the alarm with index 7:
spinserver::> event alarm show -index 7 Index 7 Module alarm Instance Motherboard Temperature 1 Variable sensorValue Status OK Current Value 33 Previous Value 33 Rising Threshold 60 Falling Threshold 27 Time Mon Dec 30 08:51:35 EST 2002 Sample Period 60
To specify the messages of warning that you want to receive and the information that you want to be sent to a remote SpinServer, use the following event filters commands:
addgrpevents
delete
modify
new
show
showeventnames
CLI:
event filters addgrpevents -name filter_name -modules [list_of_modules] -severity {debug | informational | notice | warning | error | critical | alert | emergency}
GUI: Navigate to the Event → Filters node, then select the appropriate filter from the table and run the Add Group Events command from the drop-down menu of the action pane. Enter the appropriate information into the table that is displayed and click Add Group Events.
-name filter_name
This is the name of the filter to which events are to be added. The filter must already exist.
-modules [list_of_modules]
This is the comma-separated, squared-bracketed list of software modules whose events are to be added to the filter.
-severity {debug | informational | notice | warning | error | critical | alert | emergency}
This is the severity of the events that are to be added to the filter.
The following example adds emergency events from the dblade and raid modules to a filter named sev1:
spinserver::> event filters addgrpevents -name sev1 -modules [dblade,raid] -severity emergency
CLI:
event filters delete -name filter_name
GUI: Navigate to the Event → Filters node, then select the appropriate filter from the table and run the Delete command from the drop-down menu of the action pane.
The following example deletes a filter named sev1.
spinserver::> event filters delete -name sev1
CLI:
event filters modify -name filter_name -msgids message_IDs
GUI: Navigate to the Event → Filters node, then select the appropriate filter from the table and run the Show command from the drop-down menu of the action pane. In the table that is displayed, make the appropriate modifications, then run the Modify command from the drop-down menu.
The event filters modify command modifies the list of messages that are included in an event filter.
-name filter_name
This is the name of the filter.
-msgids message_IDs
This is the list of message IDs in the filter. To list the messages that are currently in the filter, use the event filters show command. To obtain a full list of message IDs, use the event spinevents show command.
The following example modifies the sev1 filter to include message IDs 58 and 66.
spinserver::> event filters modify -name sev1 -msgids 58,66
CLI:
event filters new -name filter_name -msgids message_IDs
GUI: Navigate to the Event → Filters node, then click New in the top bar of the action pane. Enter the appropriate values into the table that is displayed and click Create.
Use the event filters new command to create a new event filter by designating the name and message IDs for the filter.
Note: To create a new filter for a particular event that occurs on a specific module, use the event spinevents createfilter command.
-name filter_name
This is the name of the filter that is to be created.
-msgids message_IDs
This is the list of message IDs that are to be added to the filter. To obtain a full list of message IDs, use the event spinevents show command.
The following example creates a new event filter named sev1 and adds message IDs 34 and 42 to it:
spinserver::> event filters new -name sev1 -msgids 34,42
CLI:
event filters show [-name filter_name]
GUI: Navigate to the Event → Filters node. To display information about a specific filter, select it from the table and run the Show command from the drop-down menu in the action pane.
The event filters show command displays the configuration information for an event filter or filters. The following information is displayed:
Filter name
Message IDs
To display the message IDs for a single event filter, use the optional -name parameter.
The following example displays the configuration information for the event filter named sev1:
spinserver::> event filters show -name sev1 Name Criticals Spin Message IDs 34, 42, 58, 66, 74, 82, 90, 98, 106, 114, 122, 130, 138, 146, 154, 162, 170, 178, 186, 194, 202, 218, 234, 242, 250, 258, 266, 274, 282, 290, 306, 322, 330
CLI:
event filters showeventnames [-name filter_name]
GUI: Navigate to the Event → Filters node. To display information about a specific filter, select it from the table and run the Show Message Names command from the drop-down menu in the action pane.
The event filters showeventnames command displays the following information for an event filter or filters:
Filter name
Message names
Message IDs
To display the message IDs for a specific event filter, use the optional -name parameter.
The following example displays the names of message IDs for an event filter named sev1:
spinserver::> event filters showeventnames -name sev1 Action "Show Message Names" returned with the following status: dblade:critical_events(34) bip:critical_events(42) dimm:critical_events(58) vldb:critical_events(66) cli:critical_events(74) raid:critical_events(82) alarm:critical_events(90) streamdaemons:critical_events(98) software:critical_events(106) vfs:critical_events(114) spinaccess:critical_events(122) audit:critical_events(130) logmsg:critical_events(138) syslog:critical_events(146) kernellog:critical_events(154) jobcontrol:critical_events(162) rootfilesystem:critical_events(170) bootimage:critical_events(178) fcddriver:critical_events(186) hamgr:critical_events(194) ivs:critical_events(202) dbladeincrcopy:critical_events(218) spinfsClient:critical_events(234) rdberrormsg:critical_events(242) vldbClient:critical_events(250) vodClient:critical_events(258) net:critical_events(266) lp:critical_events(274) spiff:critical_events(282) ndmp:critical_events(290) rpc:critical_events(306) antivirus:critical_events(322) backup:critical_events(330)
CLI:
event log show [-eid event_ID]
GUI: Navigate to the Event → Log node. Click Monitor events to display a dynamic list of events in a separate browser window, or click Show events to display a list of events in the action pane.
The event log show command displays the log records for a SpinServer. The following information is displayed:
Event ID
Time the event occurred
Severity of the event
Module in which the event occurred
Last time the event occurred
Descriptive message about the event
To view the log records for a specific event on a SpinServer, use the optional -eid parameter.
The following example displays the log records for an event with the ID 123:
spinserver::> event log show -eid 123
The following event notification handlers commands enable you to work with event-notification handlers:
delete
modify
new
show
test
CLI:
event notification handlers delete -name handler_name
GUI: Navigate to the Event → Notification → Handlers node, select the appropriate handler from the table, and run the Delete command from the drop-down menu of the action pane.
The following example deletes an event-notification handler named Server1:
spinserver::> event notification handlers delete -name Server1
CLI:
event notification handlers modify -name handler_name -parameters handler_parameters
GUI: Navigate to the Event → Notification → Handlers node, then select the appropriate handler from the table and run the Show command from the drop-down menu of the action pane. In the table that is displayed, make the appropriate modifications, then run the Modify command from the drop-down menu.
The event notification handlers modify command modifies the configuration of an event-notification handler.
-name handler_name
This is the name of the event-notification handler to be modified.
-parameters handler_parameters
This specifies parameters for the handler of event notifications. For email, the mail server address, followed by a list of email addresses, must be used. Entries in the list must be separated by commas.
This example modifies the configuration of an event-notification handler named Server1. The command specifies that the handler send event notifications to an email address named pat@acmebricks.com on a POP server named pop1.acmebricks.com.
spinserver::> event notification handlers modify -name Server1 -parameters pop1.acmebricks.com, pat@acmebricks.com
CLI:
event notification handlers new -name handler_name -type handler_type -parameters handler_parameters
GUI: Navigate to the Event → Notification → Handlers node, then click New in the top bar of the action pane. Enter the appropriate values into the table that is displayed and click Create.
-name handler_name
This is the name of the event-notification handler to be created.
-type handler_type
This is the type of the event-notification handler. Possible values are email (for one or more email addresses), snmptrap (for an SNMP trap destination), and user (for a user-defined Java class).
-parameters handler_parameters
This specifies parameters for the handler of event notifications. For email, the mail server address, followed by a list of email address, must be used. Entries in the list must be separated by commas.
This example creates an event-notification handler named Server1 that sends event notifications to the email addresses pat@acmebricks.com and chris@acmebricks.com on a POP server named pop1.acmebricks.com.
spinserver::> event notification handlers new -name Server1 -type email -parameters pop1.acmebricks.com, pat@acmebricks.com, chris@acmebricks.com
CLI:
event notification handlers show [-name handler_name]
GUI: Navigate to the Event → Notifications → Handlers node. To display information about a specific handler, select it from the table and run the Show command from the drop-down menu in the action pane.
The event notification handlers show command displays configuration information for a list of handlers of event notifications. The following information about event handlers is displayed:
Name of handler
Type of handler (email, snmptrap, or user)
Parameters for the handler
To view the configuration information for a specific event handler, use the optional -name parameter.
The following example displays configuration information for an event-notification handler named donna.
spinserver::> event notification handlers show -name donna Name donna Type email Parameters router.acmebricks.com, donna@acmebricks.com
CLI:
event notification handlers test -name handler_name
GUI: Navigate to the Event → Notification → Handlers node, select the appropriate handler from the table, and run the Test command from the drop-down menu of the action pane.
The event notification handlers test command tests an event-notification handler by sending a test message through the handler.
The following example tests an event-notification handler named Server1:
spinserver::> event notification handlers test -name Server1
CLI:
event notification history show [-eventid event_ID -host host_name]
GUI: Navigate to the Event → Notifications → History node. To display information about a specific event notification, select it from the table and run the Show command from the drop-down menu in the action pane.
The event notification history show command displays the history of event notifications for a specified host. The following information is displayed:
Host name
Event ID
The last time the notification was sent
The severity of the event
The notification message that was sent
The handler that sent the notification
The last time the event occurred
To view the log records for a specific event on a SpinServer, use the optional -host and -eventid parameters.
[-eventid event_ID]
This is the ID of the event. This parameter is optional; however, if it is used, the -host parameter must also be specified.
[-host host_name]
This is the name of the host that receives the event messages. This host cannot be part of the cluster and must be capable of receiving syslog messages. This parameter is optional; however, if it is used, the -eventid parameter must also be specified.
The following example displays the history of event notifications for event 123 on a SpinServer named Server10.
spinserver::> event notification history show -host Server10 -eventid 123
To register events to be handled, use the following event notification subscription commands:
delete
modify
new
show
CLI:
event notification subscription delete -filter filter_name -handler handler_name
GUI: Navigate to the Events → Notifications → Subscriptions node, then select the appropriate subscription from the table and run the Delete command from the drop-down menu of the action pane.
The event notification subscription delete command deletes an event-notification subscription.
-filter filter_name
This is the name of the filter.
-handler handler_name
This is the name of the handler.
The following example deletes the event-notification subscription with the filter named all_crits and the handler named email_admin:
spinserver::> event notification subscription show -filter all_crits -handler email_admin
CLI:
event notification subscription modify -filter filter_name -handler handler_name -thresholdval threshold_value -thresholdperiod threshold_period
GUI: Navigate to the Event → Notifications → Subscriptions node, then select the appropriate subscription from the table and run the Show command from the drop-down menu of the action pane. In the table that is displayed, make the appropriate modifications, then run the Modify command from the drop-down menu.
The event notification subscription modify command modifies the following attributes of an event-notification subscription:
Name
Filters
Handlers
Threshold values
Threshold time periods, specified in minutes
-filter filter_name
This is the name of the filter.
-handler handler_name
This is the name of the handler.
-thresholdval threshold_value
This is the minimum number of events that can occur before the notification is sent to the handler.
-thresholdperiod threshold_period
This is the length of time, specified in minutes, during which the threshold value is valid. If an event occurs and the time since the last transmission is greater than the threshold value, the notification is sent again.
This example modifies the configuration for an event-notification subscription with a filter named all_crits, a handler named email_admin, a threshold value of 1 event, and a threshold period of 10 minutes.
spinserver::> event notification subscription modify -filter all_crits -handler email_admin -thresholdval 1 -thresholdperiod 10
CLI:
event notification subscription new -filter filter_name -handler handler_name -thresholdval threshold_value -thresholdperiod threshold_period
GUI: Navigate to the Event → Notifications → Subscriptions node, then click New in the top bar of the action pane. Enter the appropriate values into the table that is displayed and click Create.
The event notification subscription new command creates a new event-notification subscription with the following attributes:
Filter
Handler
Threshold value
Threshold time period, specified in minutes
-filter filter_name
This is the name of the filter.
-handler handler_name
This is the name of the handler.
-thresholdval threshold_value
This is the minimum number of events that can occur before the notification is sent to the handler.
-thresholdperiod threshold_period
This is the length of time, specified in minutes, during which the threshold value is valid. If an event occurs and the time since the last transmission is greater than the threshold value, the notification is sent again.
The following example creates a new event-notification subscription with a filter named all_crits, a handler named email_admin, a threshold value of 1 event, and a threshold period of 10 minutes.
spinserver::> event notification subscription new -filter all_crits -handler email_admin -thresholdval 1 -thresholdperiod 10
CLI:
event notification subscription show [-filter filter_name -handler handler_name]
GUI: Navigate to the Event → Notification → Subscription node. To display information about a specific subscription, select it from the table and run the Show command from the drop-down menu in the action pane.
The event notification subscription show command displays the configuration information for notification subscriptions. The following information is displayed:
Module
Event name
Severity level
To display the notification subscription configuration information for a particular event, use the optional -filter and -handler parameters.
[-filter filter_name]
This is the name of the filter.
[-handler handler_name]
This is the name of the handler.
The following example displays the configuration information for the event-notification subscription to the event with the filter named all_crits and the handler named email_admin:
spinserver::> event notification subscription show -filter all_crits -handler email_admin
The event spinevents node includes the following commands:
addtofilter
createfilter
sendtestevent
show
show-group
CLI:
event spinevents addtofilter -msgid event_ID -filtername filter_name
GUI: Navigate to the Event → Event Catalog node, then select an event from the table and run the Add To Filter command from the drop-down menu of the action pane. Enter the appropriate information into the table that is displayed and click Add To Filter.
-msgid event_ID
This is the event of the ID.
-filtername filter_name
This is the name of the filter. The filter must already exist. Use the event spinevents createfilter command to create a filter.
The following example adds event ID 655480 to a filter named raid_criticals:
spinsever::> event spinevents addtofilter -msgid 655480 -filtername raid_criticals
CLI:
event spinevents createfilter -msgid event_ID -filtername filter_name
GUI: Navigate to the Event → Event Catalog node, then select an event from the table and run the Create Filter command from the drop-down menu of the action pane.
The event spinevents createfilter command specifies event ID and filter name for a new filter for a particular event. The created filter is added to the filter table.
-msgid event_ID
This is the ID of the event.
-filtername filter_name
This is the name of the filter.
The following example creates a filter named raid_criticals with event ID 82:
spinserver::> event spinevents createfilter -msgid 82 -filtername raid_criticals
CLI:
event spinevents sendtestevent -msgid event_ID
GUI: Navigate to the Event → Event Catalog node, then select an event from the table and run the Send Test Event command from the drop-down menu of the action pane.
The event spinevents sendtestevent command sends a test event message. If you issue the command with the ID of a single event, the command sends a single message for that event. If you issue the command with the ID of an event group, the command sends a message for each event in the group. You can obtain event IDs by using the event spinevents show and event spinevents show-group commands.
The following example sends test messages for event ID 82:
spinserver::> event spinevents sendtestevent -msgid 82
CLI:
event spinevents show [-msgid event_ID]
GUI: Navigate to the Event → Event Catalog node. To display information about a specific Spin event, select it from the table and run the Show command from the drop-down menu in the action pane.
The event spinevents show command displays the following configuration information for Spin events:
Message ID
Software module name
Event name
Event severity
Number of events (for event groups)
To display the configuration information for a particular event, specify the optional -msgid parameter.
The following example displays the configuration information for Spin event 82:
spinserver::> event spinevents show -msgid 82 Message ID 82 Module raid Name critical_events Severity critical # Events 25
CLI:
event spinevents show-group -msgid event)ID
GUI: Navigate to the Event → Event Catalog node. Select an event from the table and run the Show Group command from the drop-down menu in the action pane.
The event spinevents show-group command displays the Spin events that make up an event group. The command displays the following information:
Message ID
Software module name
Event name
Event severity
The following example displays the Spin events in event group 82:
spinserver::> event spinevents show-group -msgid 82
Message Module Name Severity
ID
655372 raid DISK DEAD critical
655385 raid DISK SOFT ID critical
655395 raid LOOPID CONFLICT critical
655401 raid RAIDSET CHECK DISK FAILED critical
655402 raid RAIDSET OFFLINE critical
655409 raid RAIDSET BADBLOCK critical
655420 raid UPS FAILED critical
655422 raid FAN FAILED critical
655425 raid POWER FAILED critical
655428 raid ENCHEAT BAD critical
655434 raid ENC ACCESS OFFLINE critical
655435 raid ENC SOFTADDR OCCURRED critical
655440 raid ENCLOSURE SHUTDOWN critical
655442 raid ENCLCOLD FAIL critical
655452 raid INSTALLATION ABORT critical
655453 raid CTL FIRMWARE MISMATCH critical
655455 raid WARM BOOT ERR critical
655479 raid CTL MIRROR TABLE ERR critical
655480 raid CTL STOP EJECTED critical
655488 raid CHN SCSI BUS DEAD critical
655490 raid CHN FIBRE DEAD critical
655506 raid CTL WRONG FIRMWARE critical
655510 raid CTL RESET FAILED critical
655511 raid CTL RESET ATTEMPT FAILED critical
655512 raid RS NEW RESET FAILED critical
The event syslog commands enable you to configure the Spin event-tracking system to send local SpinServer system events (also known as Spin events) to the syslog daemon running on a remote SpinServer. You can specify the hosts to which the events are sent and filter the events that are to be sent. The event syslog subnode includes the following leaf nodes:
delete
modify
new
show
test
CLI:
event syslog delete -host host_name -filter filter_name
GUI: Navigate to the Event → Syslog node, then select an item from the table and run the Delete command from the drop-down menu of the action pane.
-host host_name
This is the name of the host that receives the event messages.
-filter filter_name
This is the name of the filter.
The following example deletes the host configuration for a host named Server10 that is running a filter named all_crits.
spinserver::> event syslog delete -host Server10 -filter all_crits
CLI:
event syslog modify -host host_name -filter filter_name -facility facility
GUI: Navigate to the Event → Syslog node, then select the appropriate filter from the table and run the Show command from the drop-down menu of the action pane. In the table that is displayed, make the appropriate modifications, then run the Modify command from the drop-down menu.
-host host_name
This is the name of the host that receives the event messages. This host cannot be part of the cluster and must be capable of receiving syslog messages.
-filter filter_name
This is the name of the filter.
-facility facility
This is the name of the system facility. The default is user.
The following example modifies a host configuration for Spin events for the host named Server10 with the filter named raid_alerts. The facility is user.
spinserver::> event syslog new -host Server10 -filter raid_alerts -facility user
CLI:
event syslog new -host host_name -filter filter_name -facility facility
GUI: Navigate to the Event → Syslog node, then click New in the top bar of the action pane. Enter the appropriate values into the table that is displayed and click Create.
-host host_name
This is the name of the host that receives the event messages. This host cannot be part of the cluster and must be capable of receiving syslog messages.
-filter filter_name
This is the name of the filter.
-facility facility
This is the name of the system facility. The default is user.
The following example creates a host configuration for Spin events for the host named Server10 with the filter named raid_warn. The facility is user.
spinserver::> event syslog new -host Server10 -filter raid_warn -facility user
CLI:
event syslog show [-host host_name -filter filter_name]
GUI: Navigate to the Event → Syslog node. To display information about a particular host configuration, select it from the table and run the Show command from the drop-down menu in the action pane.
The event syslog show command displays a list of host configurations for Spin events. To display the configuration information for a specific host, use the optional -host parameter.
[-host host_name]
This is the name of the host that receives the event messages. This host cannot be part of the cluster and must be capable of receiving syslog messages. This parameter is optional; however, if it is used, the -filter option must also be used.
[-filter filter_name]
This is the name of the filter. This parameter is optional; however, if it is used, the -host option must also be used.
The following example displays the configuration for Spin events on the host named Server10 with a filter named all_crits.
spinserver::> event syslog new -host Server10 -filter all_crits
CLI:
event syslog test -host host_name -filter filter_name
GUI: Navigate to the Event → Syslog node, then select an item from the table and run the Test command from the drop-down menu of the action pane.
The event syslog test command tests a host configuration for Spin events by sending a test event.
Copyright © 2004 Network Appliance, Inc.; copyright © 2003, 2004 Spinnaker Networks, LLC. All rights reserved. Specifications subject to change without notice.